Add SettingsFolderLocation policy for centralized settings path control#3324
Draft
Add SettingsFolderLocation policy for centralized settings path control#3324
Conversation
Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add policy to override SettingsFolder location in SettingsManager
Add SettingsFolderLocation policy for centralized settings path control
Feb 9, 2026
Owner
|
…ndicator Co-authored-by: BornToBeRoot <16019165+BornToBeRoot@users.noreply.github.com>
Contributor
Author
All three items addressed in commit a58b7e0:
The UI now shows the admin indicator below the Location field when The Location field will display the policy-controlled path with the shield icon and accent-colored message when managed by policy. |
5 tasks
Removed reference to the 'Available Policies' section.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Changes proposed in this pull request
SettingsFolderLocationnullable string property toPolicyInfofor path overrideSettingsManager.GetSettingsFolderLocation()to check policy before falling back to portable/non-portable defaultssettings.mdwith System-Wide Policy info box matching existing pattern fromupdate.mdsystem-wide-policies.mdto avoid duplication (policies documented in respective setting pages)IsLocationManagedByPolicyproperty and admin shield icon) in Settings view to show when location is managed by policyImplementation:
config.json example:
{ "Update_CheckForUpdatesAtStartup": false, "SettingsFolderLocation": "C:\\CustomPath\\NETworkManager\\Settings" }UI Enhancement:
The Settings view now displays a shield icon with "This setting is managed by your administrator" message when the location is controlled by policy, matching the existing pattern in the Update settings view.
Related issue(s)
Based on PR #3313 - System-wide policy infrastructure
Copilot generated summary
Copilot summary
This PR adds
SettingsFolderLocationpolicy to enable administrators to centrally control settings storage location across all users. The implementation validates policy-provided paths (absolute, valid characters, directory not file) and falls back to defaults on validation failure. Documentation restructured to follow existing pattern with System-Wide Policy info boxes in setting pages. UI enhanced with admin indicator (shield icon + message) when location is managed by policy, matching the Update view pattern.To-Do
Contributing
By submitting this pull request, I confirm the following:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.